<html>
<head>
<title>PlPN User Documentation</title>
<link rel="stylesheet" href="PlPN.css" type="text/css" />
</head>
<body>
<h1>User Documentation</h1>

<h2>Installing scripts</h2>

<p>Installing scripts is quite easy. Simply download the script and put it
in the <code>scripts</code> subfolder inside the Programmer's Notepad
folder.</p>

<p>Uninstalling scripts is just as easy. Simply delete the script file from
the <code>scripts</code> folder.</p>

<p>You can also temporarily disable scripts by changing the file extension.
The plugin will load any files in the <code>scripts</code> folder that have
the extension <code>.pl</code>.</p>

<h2>Customization</h2>

<p>Customization in described in the
<a href="PlPN.html#customization">developer documentation</a>.</p>

<h2>Menu items</h2>

<p>After loading PlPN, you will find the PlPN menu under
<code>Extensions|PlPN</code>.</p>

<dl>
	<dt><b>Cycle Perl Interpreter</b></dt>
	<dd>If the Perl interpreter has been running for a while, it may be
	using a lot of memory and slowing down Programmer's Notepad. Cycling
	allows that memory to be released without shutting down and restarting
	the entire program.</dd>
<p></p>
	<dt><b>Select Perl DLL</b></dt>
	<dd>PlPN will make a valiant effort to find your Perl DLL, but if it is
	not named according to standard conventions, or if it is not on the
	path, it will fail. If this happens, or if you have multiple Perls
	installed, and PlPN did not find the one you want, you can set it
	explicitly here. Standard (for Windows) DLL loading rules apply: if the
	DLL is on the path, you only need the filename, and the
	<code>.dll</code> extension may be omitted, although other extensions
	may not.</dd>
<p></p>
	<dt><b>Help</b></dt>
	<dd>Surprisingly enough, this pulls up this help file.</dd>
</dl>

</body>
</html>
